BBS in a Box 15/BBS in a box XV-2.iso/Files II/Updates/General/Symantec PPC C++8.0.1 Upd.sit/SPM 8.0.1 Update/Release Notes/Debugger Release Notes/Debugger Release Notes

Text File | 1995-05-04 | 5.4 KB | 137 lines | [TEXT/SPM ]

Symantec Debugger 1.0.1 Release notes
-------------------------------------

These notes document new features and bug fixes implemented in the 1.0.1 Symantec Debugger.
Where available, defect numbers (“bug numbers”) are associated with individual items.

Bug Fixes
=========

- 9399: fixed crash with debugging in files that generate more than 32K of code
  (most notably UApplication.cp in MacApp)

- fixed problems with restoring breakpoints and expressions which could
  cause crashes

- breakpoints and expressions now "follow" lines if the source around them
  is edited. (Fix in SPM)

- breakpoints or expressions that no longer correspond with debuggable source
  are not restored

- 9528: fixed bugs with closing file (could cause crash under System 7.5.1)

- memory leaks fixed

- projects with "wraparound" TOC (negative offsets for TOC data) will no longer
  produce "bus error" messages for expressions evaluated in the Data pane

- saved expressions now contain the length and starting location of expanded arrays

- Step In now works across virtual functions (calls via _ptrgl) correctly

- now prevents you from attempting to do a Step Out from PPC code
  to an outer 68k frame

- 9454: Print and Page Setup are now disabled when the Stack or Data panes
  are selected. Before, printing these panes could cause odd behavior.

- Monitor menu item no longer enabled if MacsBug (or any low-level debugger
  that uses the MacJmp interface) is not present. Before it would hang if used.

- fixed problem where the nested function call arrow would appear in
  incorrect places

- 9298: compiler generated routines on the stack are now correctly identified

- fixed bug where debugger would perform a cleanup operation twice when
  quitting which could cause crashes in some cases


Cosmetic Fixes
==============

- fixed problems with updates when a window spanned more than one monitor,
  where the monitors had different bit depths

- changed appearence of Control Palette buttons on color monitors to better
  conform with emerging 3d Button standards

- floating palette is now correctly obscured by the Prefs and Edit Array
  Bounds dialog

- Source Not Available message in Code pane now appears correctly on multibyte
  (Kanji) systems. As a side effect, the message appears in Geneva 9 instead
  of Monoca 9 on non-multibyte systems


Fixes in DebugServices 2.0b14
=============================

- compatible with System 7.5 Update (System 7.5.1)

- 8481
  8958
  9175: stepping over toolbox routines that call WaitNextEvent/GetNextEvent no
  longer hangs the debugger (eg ModalDialog, SFGetFile, etc.)


Known Bugs
==========

- Some kinds of objects do not display correctly in the Stack Crawl pane. These
  objects will display correctly when copied to the Data pane. The affected
  objects are:
      - references
      - local statics
      - bitfields
  These bugs will be fixed in the next release of the Debugger.

- Using Go Until Here (or option-clicking on a breakpoint) will display an error
  message if the application is currently running. This error message is benign
  and can be ignored; the temporary breakpoint is set correctly and will be
  triggered when it’s encountered.

- GetScrap() may return error -108 while debugging. A workaround for this bug
  is in the latest TCL; to work around this bug in your own code, call ZeroScrap()
  if GetScrap() returns -108 (memFullErr).

- If you Step over a call to DebugStr(), the string passed to DebugStr() will not
  be displayed in the Log window.

- If an application’s partition is too small and fails to launch, the Debugger
  may not be able to provide a meaningful error message describing the problem.
  Applications that have this problem will not produce any error message if you
  try and launch them from the Finder (in other words, they will open and then
  close immediately without actually starting up). This problem can be fixed by
  increasing the partition size of the application you’re trying to debug.
  Remember that any SIZE resource added to your project will override the settings
  in the Project Options dialog.

- Option-clicking on the title bar when a source pane is displaying "no debug
  information available" may cause the Debugger to crash.

- If you attempt to option-expand a structure in the stack crawl or data pane
  that has recursive pointers, the Debugger may hang (in an infinite loop).

- If you use the newer MacsBug (version 6.5d12), you may see spurious exceptions
  in MacsBug while running the Debugger. These errors occur when the Debugger
  is asked to display the contents of invalid pointers. To work around the problem,
  use GP to exit from MacsBug; this will propogate the error to the Debugger, so
  it can display a "bus error" message. Earlier versions of MacsBug (such as version
  6.5d9) do not conflict with the Debugger in this way.

- DebugServices for Power Mac is incompatible with RAM Doubler from Connectix.
  If RAM Doubler is running while you try to use the Symantec Debugger, it will
  fail to function properly. Apple and Connectix are working on fixing this
  problem.

- If you have the Debugger Nub Controls installed (for two machine Power Mac
  debugging), make sure that it's Not Active when using the Symantec Debugger. To
  do this, open up the Debugger Nub Controls panel and make sure that the Active
  checkbox is unchecked. If it's active, the Debugger will function correctly but
  many operations will be extremely slow, and the mouse will freeze while
  performing certain debugger operations.